Method, apparatus, and system for plugin mechanism of computer extension bus

ABSTRACT

Method, apparatus, and system of detecting a hot-plug event. The hot-plug event detection may be done in-band or out-of-band. The in-band detection is performed by a state machine and the out-of-band detection is performed by a logic. A circuitry is to detect a hot-plug event when inserting or removing a device from an extension bus of the plurality of extension bus slots. The circuit is to generate a hot-plug message to notify the hot-plug event. The circuitry including the state machine, the logic and a register to provide at least two bits to mask at least two states of the state machine.

TECHNICAL FIELD

This disclosure pertains to computing systems and, in particular (but not exclusively), to a plugin mechanism of a computer bus.

BACKGROUND

Peripheral Component Interconnect (PCI) configuration space is utilized by systems employing PCI, PCI-X, and PCI Express (PCIe) to perform configuration tasks of PCI-based devices. PCI-based devices have an address space for device configuration registers referred to as configuration space, and PCI Express introduces extended configuration space for devices. Configuration space registers are typically mapped to memory mapped input/output locations by the host processor. Device drivers, operating systems, and diagnostic software access the configuration space and can read and write information to configuration space registers.

One of the improvements the PCI Local Bus had over other I/O architectures was its configuration mechanism. In addition to the normal memory-mapped and I/O port spaces, each device function on the bus has a configuration space, which is 256 bytes long, addressable by knowing the eight-bit PCI bus, five-bit device, and three-bit function numbers for the device (commonly referred to as the BDF or B/D/F, as abbreviated from bus/device/function). This allows up to 256 buses, each with up to 32 devices, each supporting eight functions. A single PCI expansion card can respond as a device and can implement at least a function number zero. The first 64 bytes of configuration space are standardized; the remainder are available specification defined extensions and/or for vendor-defined purposes.

In order to allow more parts of configuration space to be standardized without conflicting with existing uses, there can be a list of capabilities defined within the first 192 bytes of Peripheral Component Interface configuration space. Each capability has one byte that describes which capability it is, and one byte to point to the next capability. The number of additional bytes depends on the capability ID. If capabilities are being used, a bit in the Status register is set, and a pointer to the first in a linked list of capabilities is provided. Previous versions of PCIe have been provided with similar features, such as a PCIe extended capabilities structure.

BRIEF DESCRIPTION OF THE DRAWINGS

For simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity of presentation. Furthermore, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. The figures are listed below.

FIG. 1 illustrates a demonstrative embodiment of a block diagram for a computing system including a multicore processor.

FIG. 2 illustrates a demonstrative embodiment of a computing system including a peripheral component interconnect express (PCIe) compliant architecture.

FIG. 3 illustrates a demonstrative embodiment of a PCIe compliant interconnect architecture including a layered stack.

FIG. 4 illustrates a demonstrative embodiment of a PCIe compliant request or packet to be generated or received within an exemplary interconnect architecture.

FIG. 5 illustrates a demonstrative embodiment of a transmitter and receiver pair for a PCIe compliant interconnect architecture.

FIG. 6 illustrates a demonstrative embodiment of a PCIe Link Training and Status State Machine (LTSSM) state machine.

FIG. 7 illustrates a demonstrative embodiment of detection of a hot plug event in a PCIe state machine.

FIG. 8, illustrates a demonstrative embodiment of circuitry and logic to support hot plug of a device to a PCIe slot/connector.

FIG. 9 illustrates a demonstrative embodiment of a method to detect a hot-plug event.

FIG. 10 illustrates another demonstrative embodiment of a block diagram for a computing system.

FIG. 11 illustrates a demonstrative embodiment of a block diagram of components of a computer system.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forth, such as examples of specific types of processors and system configurations, specific hardware structures, specific architectural and micro architectural details, specific register configurations, specific instruction types, specific system components, specific measurements/heights, specific processor pipeline stages and operation etc. in order to provide a thorough understanding of the present disclosure. It will be apparent, however, to one skilled in the art that these specific details need not be employed to practice the present disclosure. In other instances, well known components or methods, such as specific and alternative processor architectures, specific logic circuits/code for described algorithms, specific firmware code, specific interconnect operation, specific logic configurations, specific manufacturing techniques and materials, specific compiler implementations, specific expression of algorithms in code, specific power down and gating techniques/logic and other specific operational details of computer system haven't been described in detail in order to avoid unnecessarily obscuring the present disclosure.

Although the following embodiments may be described with reference to energy conservation and energy efficiency in specific integrated circuits, such as in computing platforms or microprocessors, other embodiments are applicable to other types of integrated circuits and logic devices. Similar techniques and teachings of embodiments described herein may be applied to other types of circuits or semiconductor devices that may also benefit from better energy efficiency and energy conservation. For example, the disclosed embodiments are not limited to desktop computer systems or Ultrabooks™, and may be also used in other devices, such as handheld devices, tablets, other thin notebooks, systems on a chip (SOC) devices, and embedded applications. Some examples of handheld devices include cellular phones, Internet protocol devices, digital cameras, personal digital assistants (PDAs), and handheld PCs. Embedded applications typically include a microcontroller, a digital signal processor (DSP), a system on a chip, network computers (NetPC), set-top boxes, network hubs, wide area network (WAN) switches, or any other system that can perform the functions and operations taught below. Moreover, the apparatus′, methods, and systems described herein are not limited to physical computing devices, but may also relate to software optimizations for energy conservation and efficiency. As will become readily apparent in the description below, the embodiments of methods, apparatus', and systems described herein (whether in reference to hardware, firmware, software, or a combination thereof) are vital to a ‘green technology’ future balanced with performance considerations.

As computing systems are advancing, the components therein are becoming more complex. As a result, the interconnect architecture to couple and communicate between the components is also increasing in complexity to ensure bandwidth requirements are met for optimal component operation. Furthermore, different market segments demand different aspects of interconnect architectures to suit the market's needs. For example, servers require higher performance, while the mobile ecosystem is sometimes able to sacrifice overall performance for power savings. Yet, it's a singular purpose of most fabrics to provide highest possible performance with maximum power saving. Below, a number of interconnects are discussed, which would potentially benefit from aspects of the disclosure described herein.

Referring to FIG. 1, an embodiment of a block diagram for a computing system including a multicore processor is depicted. Processor 100 includes any processor or processing device, such as a microprocessor, an embedded processor, a digital signal processor (DSP), a network processor, a handheld processor, an application processor, a co-processor, a system on a chip (SOC), or other device to execute code. Processor 100, in one embodiment, includes at least two cores, e.g., core 101 and 102, which may include asymmetric cores or symmetric cores (the illustrated embodiment). However, processor 100 may include any number of processing elements that may be symmetric or asymmetric.

In one embodiment, a processing element refers to hardware or logic to support a software thread. Examples of hardware processing elements include: a thread unit, a thread slot, a thread, a process unit, a context, a context unit, a logical processor, a hardware thread, a core, and/or any other element, which is capable of holding a state for a processor, such as an execution state or architectural state. In other words, a processing element, in one embodiment, refers to any hardware capable of being independently associated with code, such as a software thread, operating system, application, or other code. A physical processor (or processor socket) typically refers to an integrated circuit, which potentially includes any number of other processing elements, such as cores or hardware threads.

A core often refers to logic located on an integrated circuit capable of maintaining an independent architectural state, wherein each independently maintained architectural state is associated with at least some dedicated execution resources. In contrast to cores, a hardware thread typically refers to any logic located on an integrated circuit capable of maintaining an independent architectural state, wherein the independently maintained architectural states share access to execution resources. As can be seen, when certain resources are shared and others are dedicated to an architectural state, the line between the nomenclature of a hardware thread and core overlaps. Yet often, a core and a hardware thread are viewed by an operating system as individual logical processors, where the operating system is able to individually schedule operations on each logical processor.

Physical processor 100, as illustrated in FIG. 1, includes two cores—core 101 and 102. Here, core 101 and 102 are considered symmetric cores, i.e. cores with the same configurations, functional units, and/or logic. In another embodiment, core 101 includes an out-of-order processor core, while core 102 includes an in-order processor core. However, cores 101 and 102 may be individually selected from any type of core, such as a native core, a software managed core, a core adapted to execute a native Instruction Set Architecture (ISA), a core adapted to execute a translated Instruction Set Architecture (ISA), a co-designed core, or other known core. In a heterogeneous core environment (i.e. asymmetric cores), some form of translation, such a binary translation, may be utilized to schedule or execute code on one or both cores. Yet to further the discussion, the functional units illustrated in core 101 are described in further detail below, as the units in core 102 operate in a similar manner in the depicted embodiment.

As depicted, core 101 includes two hardware threads 101 a and 101 b, which may also be referred to as hardware thread slots 101 a and 101 b. Therefore, software entities, such as an operating system, in one embodiment potentially view processor 100 as four separate processors, i.e., four logical processors or processing elements capable of executing four software threads concurrently. As alluded to above, a first thread is associated with architecture state registers 101 a, a second thread is associated with architecture state registers 101 b, a third thread may be associated with architecture state registers 102 a, and a fourth thread may be associated with architecture state registers 102 b. Here, each of the architecture state registers (101 a, 101 b, 102 a, and 102 b) may be referred to as processing elements, thread slots, or thread units, as described above. As illustrated, architecture state registers 101 a are replicated in architecture state registers 101 b, so individual architecture states/contexts are capable of being stored for logical processor 101 a and logical processor 101 b. In core 101, other smaller resources, such as instruction pointers and renaming logic in allocator and renamer block 130 may also be replicated for threads 101 a and 101 b. Some resources, such as re-order buffers in reorder/retirement unit 135, ILTB 120, load/store buffers, and queues may be shared through partitioning. Other resources, such as general purpose internal registers, page-table base register(s), low-level data-cache and data-TLB 115, execution unit(s) 140, and portions of out-of-order unit 135 are potentially fully shared.

Processor 100 often includes other resources, which may be fully shared, shared through partitioning, or dedicated by/to processing elements. In FIG. 1, an embodiment of a purely exemplary processor with illustrative logical units/resources of a processor is illustrated. Note that a processor may include, or omit, any of these functional units, as well as include any other known functional units, logic, or firmware not depicted. As illustrated, core 101 includes a simplified, representative out-of-order (OOO) processor core. But an in-order processor may be utilized in different embodiments. The OOO core includes a branch target buffer 120 to predict branches to be executed/taken and an instruction-translation buffer (I-TLB) 120 to store address translation entries for instructions.

Core 101 further includes decode module 125 coupled to fetch unit 120 to decode fetched elements. Fetch logic, in one embodiment, includes individual sequencers associated with thread slots 101 a, 101 b, respectively. Usually core 101 is associated with a first ISA, which defines/specifies instructions executable on processor 100. Often machine code instructions that are part of the first ISA include a portion of the instruction (referred to as an opcode), which references/specifies an instruction or operation to be performed. Decode logic 125 includes circuitry that recognizes these instructions from their opcodes and passes the decoded instructions on in the pipeline for processing as defined by the first ISA. For example, as discussed in more detail below decoders 125, in one embodiment, include logic designed or adapted to recognize specific instructions, such as transactional instruction. As a result of the recognition by decoders 125, the architecture or core 101 takes specific, predefined actions to perform tasks associated with the appropriate instruction. It is important to note that any of the tasks, blocks, operations, and methods described herein may be performed in response to a single or multiple instructions; some of which may be new or old instructions. Note decoders 126, in one embodiment, recognize the same ISA (or a subset thereof). Alternatively, in a heterogeneous core environment, decoders 126 recognize a second ISA (either a subset of the first ISA or a distinct ISA).

In one example, allocator and renamer block 130 includes an allocator to reserve resources, such as register files to store instruction processing results. However, threads 101 a and 101 b are potentially capable of out-of-order execution, where allocator and renamer block 130 also reserves other resources, such as reorder buffers to track instruction results. Unit 130 may also include a register renamer to rename program/instruction reference registers to other registers internal to processor 100. Reorder/retirement unit 135 includes components, such as the reorder buffers mentioned above, load buffers, and store buffers, to support out-of-order execution and later in-order retirement of instructions executed out-of-order.

Scheduler and execution unit(s) block 140, in one embodiment, includes a scheduler unit to schedule instructions/operation on execution units. For example, a floating point instruction is scheduled on a port of an execution unit that has an available floating point execution unit. Register files associated with the execution units are also included to store information instruction processing results. Exemplary execution units include a floating point execution unit, an integer execution unit, a jump execution unit, a load execution unit, a store execution unit, and other known execution units.

Lower level data cache and data translation buffer (D-TLB) 150 are coupled to execution unit(s) 140. The data cache is to store recently used/operated on elements, such as data operands, which are potentially held in memory coherency states. The D-TLB is to store recent virtual/linear to physical address translations. As a specific example, a processor may include a page table structure to break physical memory into a plurality of virtual pages.

Here, cores 101 and 102 share access to higher-level or further-out cache, such as a second level cache associated with on-chip interface 110. Note that higher-level or further-out refers to cache levels increasing or getting further way from the execution unit(s). In one embodiment, higher-level cache is a last-level data cache—last cache in the memory hierarchy on processor 100—such as a second or third level data cache. However, higher level cache is not so limited, as it may be associated with or include an instruction cache. A trace cache—a type of instruction cache—instead may be coupled after decoder 125 to store recently decoded traces. Here, an instruction potentially refers to a macro-instruction (i.e. a general instruction recognized by the decoders), which may decode into a number of micro-instructions (micro-operations).

In the depicted configuration, processor 100 also includes on-chip interface module 110. Historically, a memory controller, which is described in more detail below, has been included in a computing system external to processor 100. In this scenario, on-chip interface 110 is to communicate with devices external to processor 100, such as system memory 175, a chipset (often including a memory controller hub to connect to memory 175 and an I/O controller hub to connect peripheral devices), a memory controller hub, a northbridge, or other integrated circuit. And in this scenario, bus 105 may include any known interconnect, such as multi-drop bus, a point-to-point interconnect, a serial interconnect, a parallel bus, a coherent (e.g. cache coherent) bus, a layered protocol architecture, a differential bus, and a GTL bus.

Memory 175 may be dedicated to processor 100 or shared with other devices in a system. Common examples of types of memory 175 include DRAM, SRAM, non-volatile memory (NV memory), and other known storage devices. Note that device 180 may include a graphic accelerator, processor or card coupled to a memory controller hub, data storage coupled to an I/O controller hub, a wireless transceiver, a flash device, an audio controller, a network controller, or other known device.

Recently however, as more logic and devices are being integrated on a single die, such as SOC, each of these devices may be incorporated on processor 100. For example in one embodiment, a memory controller hub is on the same package and/or die with processor 100. Here, a portion of the core (an on-core portion) 110 includes one or more controller(s) for interfacing with other devices such as memory 175 or a graphics device 180. The configuration including an interconnect and controllers for interfacing with such devices is often referred to as an on-core (or un-core configuration). As an example, on-chip interface 110 includes a ring interconnect for on-chip communication and a high-speed serial point-to-point link 105 for off-chip communication. Yet, in the SOC environment, even more devices, such as the network interface, co-processors, memory 175, graphics processor 180, and any other known computer devices/interface may be integrated on a single die or integrated circuit to provide small form factor with high functionality and low power consumption.

In one embodiment, processor 100 is capable of executing a compiler, optimization, and/or translator code 177 to compile, translate, and/or optimize application code 176 to support the apparatus and methods described herein or to interface therewith. A compiler often includes a program or set of programs to translate source text/code into target text/code. Usually, compilation of program/application code with a compiler is done in multiple phases and passes to transform hi-level programming language code into low-level machine or assembly language code. Yet, single pass compilers may still be utilized for simple compilation. A compiler may utilize any known compilation techniques and perform any known compiler operations, such as lexical analysis, preprocessing, parsing, semantic analysis, code generation, code transformation, and code optimization.

Larger compilers often include multiple phases, but most often these phases are included within two general phases: (1) a front-end, i.e. generally where syntactic processing, semantic processing, and some transformation/optimization may take place, and (2) a back-end, i.e. generally where analysis, transformations, optimizations, and code generation takes place. Some compilers refer to a middle, which illustrates the blurring of delineation between a front-end and back end of a compiler. As a result, reference to insertion, association, generation, or other operation of a compiler may take place in any of the aforementioned phases or passes, as well as any other known phases or passes of a compiler. As an illustrative example, a compiler potentially inserts operations, calls, functions, etc. in one or more phases of compilation, such as insertion of calls/operations in a front-end phase of compilation and then transformation of the calls/operations into lower-level code during a transformation phase. Note that during dynamic compilation, compiler code or dynamic optimization code may insert such operations/calls, as well as optimize the code for execution during runtime. As a specific illustrative example, binary code (already compiled code) may be dynamically optimized during runtime. Here, the program code may include the dynamic optimization code, the binary code, or a combination thereof.

Similar to a compiler, a translator, such as a binary translator, translates code either statically or dynamically to optimize and/or translate code. Therefore, reference to execution of code, application code, program code, or other software environment may refer to: (1) execution of a compiler program(s), optimization code optimizer, or translator either dynamically or statically, to compile program code, to maintain software structures, to perform other operations, to optimize code, or to translate code; (2) execution of main program code including operations/calls, such as application code that has been optimized/compiled; (3) execution of other program code, such as libraries, associated with the main program code to maintain software structures, to perform other software related operations, or to optimize code; or (4) a combination thereof.

One interconnect fabric architecture includes PCIe architecture. A primary goal of PCIe is to enable components and devices from different vendors to inter-operate in an open architecture, spanning multiple market segments; Clients (Desktops and Mobile), Servers (Standard and Enterprise), and Embedded and Communication devices. PCI Express is a high performance, general purpose I/O interconnect defined for a wide variety of future computing and communication platforms. Some PCI attributes, such as its usage model, load-store architecture, and software interfaces, have been maintained through its revisions, whereas previous parallel bus implementations have been replaced by a highly scalable, fully serial interface. The more recent versions of PCI Express take advantage of advances in point-to-point interconnects, Switch-based technology, and packetized protocol to deliver new levels of performance and features. Power Management, Quality Of Service (QoS), Hot-Plug/Hot-Swap support, Data Integrity, and Error Handling are among some of the advanced features supported by PCI Express.

Referring to FIG. 2, an embodiment of a fabric composed of point-to-point Links that interconnect a set of components is illustrated. System 200 includes processor 205 and system memory 210 coupled to controller hub 215. Processor 205 includes any processing element, such as a microprocessor, a host processor, an embedded processor, a co-processor, or other processor. Processor 205 is coupled to controller hub 215 through front-side bus (FSB) 206. In one embodiment, FSB 206 is a serial point-to-point interconnect as described below. In another embodiment, link 206 includes a serial, differential interconnect architecture that is compliant with a different interconnect standard.

System memory 210 includes any memory device, such as random access memory (RAM), non-volatile (NV) memory, or other memory accessible by devices in system 200. System memory 210 is coupled to controller hub 215 through memory interface 216. Examples of a memory interface include a double-data rate (DDR) memory interface, a dual-channel DDR memory interface, and a dynamic RAM (DRAM) memory interface.

In one embodiment, controller hub 215 is a root hub, root complex, or root controller in a Peripheral Component Interconnect Express (PCIe or PCIE) interconnection hierarchy. Examples of controller hub 215 include a chipset, a memory controller hub (MCH), a northbridge, an interconnect controller hub (ICH) a southbridge, and a root controller/hub. Often the term chipset refers to two physically separate controller hubs, i.e. a memory controller hub (MCH) coupled to an interconnect controller hub (ICH). Note that current systems often include the MCH integrated with processor 205, while controller 215 is to communicate with I/O devices, in a similar manner as described below. In some embodiments, peer-to-peer routing is optionally supported through root complex 215.

Here, controller hub 215 is coupled to switch/bridge 220 through serial link 219. Input/output modules 217 and 221, which may also be referred to as interfaces/ports 217 and 221, include/implement a layered protocol stack to provide communication between controller hub 215 and switch 220. In one embodiment, multiple devices are capable of being coupled to switch 220.

Switch/bridge 220 routes packets/messages from device 225 upstream, i.e. up a hierarchy towards a root complex, to controller hub 215 and downstream, i.e. down a hierarchy away from a root controller, from processor 205 or system memory 210 to device 225. Switch 220, in one embodiment, is referred to as a logical assembly of multiple virtual PCI-to-PCI bridge devices. Device 225 includes any internal or external device or component to be coupled to an electronic system, such as an I/O device, a Network Interface Controller (NIC), an add-in card, an audio processor, a network processor, a hard-drive, a storage device, a CD/DVD ROM, a monitor, a printer, a mouse, a keyboard, a router, a portable storage device, a Firewire device, a Universal Serial Bus (USB) device, a scanner, and other input/output devices. Often in the PCIe vernacular, such as device, is referred to as an endpoint. Although not specifically shown, device 225 may include a PCIe to PCI/PCI-X bridge to support legacy or other version PCI devices. Endpoint devices in PCIe are often classified as legacy, PCIe, or root complex integrated endpoints.

Graphics accelerator 230 is also coupled to controller hub 215 through serial link 232. In one embodiment, graphics accelerator 230 is coupled to an MCH, which is coupled to an ICH. Switch 220, and accordingly I/O device 225, is then coupled to the ICH. I/O modules 231 and 218 are also to implement a layered protocol stack to communicate between graphics accelerator 230 and controller hub 215. Similar to the MCH discussion above, a graphics controller or the graphics accelerator 230 itself may be integrated in processor 205.

Turning to FIG. 3, an embodiment of a layered protocol stack is illustrated. Layered protocol stack 300 includes any form of a layered communication stack, such as, for example a Quick Path Interconnect (QPI) stack, a PCIe stack, a next generation high performance computing interconnect stack, or other layered stack. In one embodiment, protocol stack 300 is a PCIe protocol stack including transaction layer 305, link layer 310, and physical layer 320. An interface, such as interfaces 217, 218, 221, 222, 226, and 231 in FIG. 2, may be represented as communication protocol stack 300. Representation as a communication protocol stack may also be referred to as a module or interface implementing/including a protocol stack.

PCI Express uses packets to communicate information between components. Packets are formed in the Transaction Layer 305 and Data Link Layer 310 to carry the information from the transmitting component to the receiving component. As the transmitted packets flow through the other layers, they are extended with additional information necessary to handle packets at those layers. At the receiving side the reverse process occurs and packets get transformed from their Physical Layer 320 representation to the Data Link Layer 310 representation and finally (for Transaction Layer Packets) to the form that can be processed by the Transaction Layer 305 of the receiving device.

Transaction Layer

In one embodiment, transaction layer 305 is to provide an interface between a device's processing core and the interconnect architecture, such as data link layer 310 and physical layer 320. In this regard, a primary responsibility of the transaction layer 305 is the assembly and disassembly of packets (i.e., transaction layer packets, or TLPs). The translation layer 305 may manage credit-base flow control for TLPs. PCIe implements split transactions, i.e. transactions with request and response separated by time, allowing a link to carry other traffic while the target device gathers data for the response.

In addition, PCIe utilizes credit-based flow control. In this scheme, a device advertises an initial amount of credit for each of the receive buffers in Transaction Layer 305. An external device at the opposite end of the link, such as controller hub 215 in FIG. 2, counts the number of credits consumed by each TLP. A transaction may be transmitted if the transaction does not exceed a credit limit. Upon receiving a response an amount of credit is restored. An advantage of a credit scheme is that the latency of credit return does not affect performance, provided that the credit limit is not encountered.

In one embodiment, four transaction address spaces include a configuration address space, a memory address space, an input/output address space, and a message address space. Memory space transactions include one or more of read requests and write requests to transfer data to/from a memory-mapped location. In one embodiment, memory space transactions are capable of using two different address formats, e.g., a short address format, such as a 32-bit address, or a long address format, such as 64-bit address. Configuration space transactions are used to access configuration space of the PCIe devices. Transactions to the configuration space include read requests and write requests. Message space transactions (or, simply messages) are defined to support in-band communication between PCIe agents.

Therefore, in one embodiment, transaction layer 305 assembles packet header/payload 306. Format for current packet headers/payloads may be found in the PCIe specification at the PCIe specification website.

Quickly referring to FIG. 4, an embodiment of a PCIe transaction descriptor is illustrated. In one embodiment, transaction descriptor 400 is a mechanism for carrying transaction information. In this regard, transaction descriptor 400 supports identification of transactions in a system. Other potential uses include tracking modifications of default transaction ordering and association of transaction with channels.

Transaction descriptor 400 includes global identifier (ID) field 402, attributes field 404 and channel identifier field 406. In the illustrated example, global identifier field 402 is depicted comprising local transaction identifier field 408 and source identifier field 410. In one embodiment, global transaction identifier 402 is unique for all outstanding requests.

According to one implementation, local transaction identifier field 408 is a field generated by a requesting agent, and it is unique for all outstanding requests that require a completion for that requesting agent. Furthermore, in this example, source identifier 410 uniquely identifies the requestor agent within a PCIe hierarchy. Accordingly, together with source ID 410, local transaction identifier field 408 provides global identification of a transaction within a hierarchy domain.

Attributes field 404 specifies characteristics and relationships of the transaction. In this regard, attributes field 404 is potentially used to provide additional information that allows modification of the default handling of transactions. In one embodiment, attributes field 404 includes priority field 412, reserved field 414, ordering field 416, and no-snoop field 418. Here, priority sub-field 412 may be modified by an initiator to assign a priority to the transaction. Reserved attribute field 414 is left reserved for future, or vendor-defined usage. Possible usage models using priority or security attributes may be implemented using the reserved attribute field.

In this example, ordering attribute field 416 is used to supply optional information conveying the type of ordering that may modify default ordering rules. According to one example implementation, an ordering attribute of “0” denotes default ordering rules are to apply, wherein an ordering attribute of “1” denotes relaxed ordering, wherein writes can pass writes in the same direction, and read completions can pass writes in the same direction. Snoop attribute field 418 is utilized to determine if transactions are snooped. As shown, channel ID Field 406 identifies a channel that a transaction is associated with.

Link Layer

Link layer 310, also referred to as data link layer 310, acts as an intermediate stage between transaction layer 305 and the physical layer 320. In one embodiment, a responsibility of the data link layer 310 is providing a reliable mechanism for exchanging Transaction Layer Packets (TLPs) between two components a link. One side of the Data Link Layer 310 accepts TLPs assembled by the Transaction Layer 305, applies packet sequence identifier 311, i.e. an identification number or packet number, calculates and applies an error detection code, i.e. CRC 312, and submits the modified TLPs to the Physical Layer 320 for transmission across a physical to an external device.

Physical Layer

In one embodiment, physical layer 320 includes logical sub block 321 and electrical sub-block 322 to physically transmit a packet to an external device. Here, logical sub-block 321 is responsible for the “digital” functions of Physical Layer 321. In this regard, the logical sub-block includes a transmit section to prepare outgoing information for transmission by physical sub-block 322, and a receiver section to identify and prepare received information before passing it to the Link Layer 310.

Physical block 322 includes a transmitter and a receiver. The transmitter is supplied by logical sub-block 321 with symbols, which the transmitter serializes and transmits onto to an external device. The receiver is supplied with serialized symbols from an external device and transforms the received signals into a bit-stream. The bit-stream is de-serialized and supplied to logical sub-block 321. In one embodiment, an 8b/10b transmission code is employed, where ten-bit symbols are transmitted/received. Here, special symbols are used to frame a packet with frames 323. In addition, in one example, the receiver also provides a symbol clock recovered from the incoming serial stream.

As stated above, although transaction layer 305, link layer 310, and physical layer 320 are discussed in reference to a specific embodiment of a PCIe protocol stack, a layered protocol stack is not so limited. In fact, any layered protocol may be included/implemented. As an example, a port/interface that is represented as a layered protocol includes: (1) a first layer to assemble packets, i.e. a transaction layer; a second layer to sequence packets, i.e. a link layer; and a third layer to transmit the packets, i.e. a physical layer. As a specific example, a common standard interface (CSI) layered protocol is utilized.

Referring next to FIG. 5, an embodiment of a PCIe serial point to point fabric is illustrated. Although an embodiment of a PCIe serial point-to-point link is illustrated, a serial point-to-point link is not so limited, as it includes any transmission path for transmitting serial data. In the embodiment shown, a basic PCIe link includes two, low-voltage, differentially driven signal pairs: a transmit pair 506/511 and a receive pair 512/507. Accordingly, device 505 includes transmission logic 506 to transmit data to device 510 and receiving logic 507 to receive data from device 510. In other words, two transmitting paths, i.e. paths 516 and 517, and two receiving paths, i.e. paths 518 and 519, are included in a PCIe link.

A transmission path refers to any path for transmitting data, such as a transmission line, a copper line, an optical line, a wireless communication channel, an infrared communication link, or other communication path. A connection between two devices, such as device 505 and device 510, is referred to as a link, such as link 515. A link may support one lane—each lane representing a set of differential signal pairs (one pair for transmission, one pair for reception). To scale bandwidth, a link may aggregate multiple lanes denoted by xN, where N is any supported Link width, such as 1, 2, 4, 8, 12, 16, 32, 64, or wider.

A differential pair refers to two transmission paths, such as lines 516 and 517, to transmit differential signals. As an example, when line 516 toggles from a low voltage level to a high voltage level, i.e. a rising edge, line 517 drives from a high logic level to a low logic level, i.e. a falling edge. Differential signals potentially demonstrate better electrical characteristics, such as better signal integrity, i.e. cross-coupling, voltage overshoot/undershoot, ringing, etc. This allows for better timing window, which enables faster transmission frequencies.

According to one demonstrative embodiment, PCIe interconnect may include hot-plug capabilities. The hot-plug feature may allow easy replacement and/or addition and/or removing of devices connected to PCIe slot and/or connector. For example, hot-plug enterprise-class storage such as, for example, hard disk drives (HDDs) and solid-state drives (SSDs) may externally accessible and may support PCIe hot-plug capabilities and may be easily added and/or removed and/or replaced from the PCIe slot and/or connector using PCIe hot-plug capabilities.

For example, enterprise applications may greatly benefit from PCIe connected SSDs due to performance improvements that the technology brings to such applications. Current enterprise storage systems based on Serial-attached Small Computer System Interface (SCSI) (SAS) infrastructure provides means for supporting hot-plug capability. According to one embodiment, in order to enable widespread use of PCIe SSD technology it may be extremely important to provide robust mechanisms for supporting hot-plug capability including unaccepted plug-in/plug-out of devices to the PCIe slot and/or connector. This unaccepted plug of devices to the PCIe slot and/or connector may also be termed as surprise hot-plug, if desired.

According to some embodiments, a PCIe hot-plug event may be defined as a hot removal and/or hot addition of devices to the PCIe slot and/or connector. “Hot” may be interpreted as removal or addition of devices when a system including PCIe slot is powered on.

According to one demonstrative embodiment, in a nut shell, in the event of a hot-removal or a hot-addition of, for example, a PCIe SSD, an in-band PCIe hot-plug mechanism may monitor state transitions of a Link Training and Status State Machine (LTSSM) state machine of a root port to uniquely identify the PCIe event without any external circuitry. On detecting the hot-plug event, slot register bits may be updated and one or more hot-plug messages may be generated to notify of the occurrence of the hot-plug event.

Reference is made to FIG. 6, in which an illustration of a demonstrative embodiment of a PCIe LTSSM state machine 600 is shown. According to one embodiment, the LTSSM state machine may include a Detect state 610, a Polling state 620, a Configure state 630, a L0 state 640, a L1 state 645, a L2 state 650, a LOS state 655, a recovery state 660, a disable state 670, an external loopback state 680, and/or a hot reset state 690.

According to some demonstrative embodiments, the term “Lane” may be defined as a set of differential signal pairs, one pair for transmission and one pair for reception. For example, a by-N Link may be composed of N Lanes. The term “Layer” may be used as a unit of distinction applied to this specification to help clarify the behavior of key elements. The use of the term Layer does not imply a specific implementation. The term “Link” may be defined as a collection of two Ports and their interconnecting Lanes. A Link may be a dual-simplex communications path between two components. The term “Port” may have two meanings: logically, an interface between a component and a PCI Express Link, physically, a group of transmitters and receivers located on the same chip that define a Link.

According to one embodiment, for example, the purpose of Detect state 610 is to detect when a far end termination is present. This state may be entered at any time if directed. Detect state 610 may include a Detect.Quiet sub-state and a Detect.Active sub-state (not shown in FIG. 6). In the Detect.Quiet sub-state a device, for example, a transmitter, may be in an electrical idle state and may not transmit signals. In the Detect.Active sub-state the device, for example, the transmitter, may perform a receiver detection sequence on all un-configured Lanes that can form one or more Links, if desired.

In Polling state 620, a Port may transmit training Ordered Sets and may respond to the received training Ordered Sets. In this state, bit lock and symbol lock are established and Lane polarity is configured. Polling state 620 may include a Polling.Compliance sub state, a Pulling.active sub-state, and/or a Pulling.configuration sub-state.

In Configuration state 630, both the transmitter and receiver are sending and receiving data at a negotiated data rate. The lanes of a port configure into a link through a width and lane negotiation sequence. In Recovery state 660, both the transmitter and receiver are sending and receiving data using the configured link and lane number as well as the previously supported data rate(s). Recovery state 660 may allow a configured link to change the data rate of operation if desired, re-establish bit lock, Symbol lock or block alignment, and Lane-to-Lane de-skew. Recovery is also used to enter Loopback state 680, disabled state 670, hot reset state 690, and/or Configuration state 630.

L0 state 640 is the normal operational state where data and control packets may be transmitted and received. All power management states are entered from this state. L0S state 655 is intended as a power savings state. When operating with separate reference clocks with independent Spread Spectrum Clocking (SSC), LOS is not supported and must not be advertised in the capability registers.

L1 state 645 is intended as a power savings state. L1 state 645 may allow an additional power savings over LOS state 655 at the cost of additional resume latency. The entry to L1 state 645 occurs after being directed by the Data Link Layer and receiving an Electrical Idle Ordered Set (EIOS). Power may be aggressively conserved in L2 state 650. Most elements of the transmitter and receiver may be shut off main power and clocks are not guaranteed, however auxiliary power is available. When Beacon support is required by the associated system or form factor specification, an upstream port that supports the wakeup capability must be able to send; and a downstream port may be able to receive; a wakeup signal referred to as a beacon. The entry to L2 state 650 may occur after being directed by the data link layer and receiving the EIOS.

The intent of the Disabled state 670 is to allow a configured link to be disabled until directed or electrical idle is exited (i.e., due to a hot removal and insertion) after entering disabled state 670. A link may enter Disabled state 670 if directed by a higher layer. A link may also reach the Disabled state 670 by receiving two consecutive ordered sets with the disable link bit asserted.

External Loopback state 680 is intended for test and fault isolation use. Only the entry and exit behavior is specified, all other details are implementation specific. External loopback state 680 may operate on either a per lane basis or a configured link basis.

According to a demonstrative embodiment, a spurious hot plug event may be generated when LTSSM state machine 600 transits from Detect State 610 to Polling state 620, from Polling state 620 to Configuration state 630, and/or back to Detect state 610.

Turning to FIG. 7 a demonstrative embodiment of detection of a hot plug event 740 in a PCIe state machine 700 is shown. For example, hot-plug event 740 may be handled by PCIe LTSSM 700 as follows. Coming out of reset, PCIe LTSSM state machine 700 may be in Detect state 710. Once a device is detected PCIe LTSSM state machine 700 may move from Detect state 710 to Polling state 720. In the Polling state 720, a root port (RP) ordered sets may be exchanged with the device to establish polarity and line rate, before transitioning to Configuration state 730. In the Configuration state 730 the Link width/number/reversal etc. may established before transitioning to normal operating state L0 640 (FIG. 6), if desired. According to some embodiments, RP is a PCI Express Port on a Root Complex that maps a portion of a Hierarchy through an associated virtual PCI-PCI Bridge.

In one demonstrative embodiment, the surprise hot-plug mechanism may be implemented in a server. In this embodiment, a presence of a detected change may be logged and hence hot-plug event 740 is generated, for example, whenever the LTSSM leaves/enters either Detect state 710 or Polling state 720 from any other state such as, for example Configuration state 730, if desired.

According to another embodiment, the surprise hot-plug mechanism may be implemented in a client. In the client hot-plug implementation, while at Detect state 710, a presence of detected change may be logged and hence hot-plug event 740 may be generated, for example, whenever the LTSSM leaves/enters Detect state 710 from any other state or optionally the Detect.Active sub-state from Detect.Quiet sub-state any other state e.g., the Detect.Active state and Detect.Quiet a sub-states of Detect state 710.

Consequently, if PCIe LTSSM mechanism 700 transitions from Detect state 710 to Polling state 720 to Configuration state 730 and back to Detect state 710, and if there is failure during configuration, then two spurious hot-plug events would be generated when PCIe LTSSM mechanism 700 transitions from Polling state 720 to Configuration state 730 and from Configuration State 730 to Detect State 710. For example, a spurious Hot-Plug event 750 may occur on insertion of a device to a PCIe slot and/or connector, and a spurious Hot-Plug event 760 may occur on removal of a device from a PCIe slot and/or connector, although it should be understood that embodiments described by this example are not limiting, and other implementations may be performed by different embodiments.

Referring to FIG. 8, an exemplary embodiment of circuitry and logic 800 to support hot plug of a device to a PCIe slot/connector is shown.

For example, hot-plug circuitry 800 may include an LTSSM 810, a virtual pin port logic (VPP) 820, a system management bus (SMBus) 825, an input/output (I/O) extender 830 a PCIe slot and/or connector 840, AND gates 850, 855 and 875, a NOR gate 860, an OR gate 865, a multiplexer (MUX) 870, an edge detector 880, a Slot Status (SLOTSTS) register 882, a PCI Express capability (PXPCAP) register 884, and/or a Miscellaneous Control and Status (MISCRTLSTS) register 886.

According to at least one exemplary embodiment, hot-plug circuitry 800 may be used for Out-Of-Band (OOB) hot-plug event detection and/or for In-Band hot-plug event detection, if desired.

According to one exemplary embodiment, OOB hot-plug event detection may detect a hot insertion or removal of a device from PCIe slot/connector 840. Signals notifying of the occurrence of the hot-plug event may be sent to I/O extender 830 to SMBus 825 and VPP logic 820. VPP logic 820 may send a Presence Detect signal, e.g., logic “1”, to MUX 870 and OR gate 865. MUX 870 may provide a presence detect bit, e.g., logic “1”, to AND gate 875. PXPCAP register 884 may also provide a slot implemented bit, e.g., logic “1”, to AND gate 875. The Slot Implemented bit, when set, may indicate that a Link associated with a Port is connected to PCIe slot 840. If the PORT is connected to the PCIe slot 840 and VPP logic 820 detects the hot-plug event, AND gate 875 may write to SLOTSTS register 882 that a device is connected to the PCIe slot 840, and may provide the logic “1” to edge detector 880. Edge detector 880 may write to presence detect change bit of SLOTSTS register 882 the status of the device, e.g., insertion or removal. Changes in the “Presence Detect” status in SLOTSTS register 882 may trigger a PCI hot plug event to a Hot Plug driver.

According to another demonstrative embodiment, an in-band hot-plug event detection may be used. According to this embodiment, LTSSM state machine 810 may detect the hot-plug event, for example a surprise hot-plug event, if desired. As described above with reference to FIGS. 6 and 7, LTSSM state machine 810 may provide according to different states of a hot-plug event mechanism, a Detect indication, a Polling indication, or a Configuration indication. Based on the LTSSM state definitions it is possible to determine if a device is connected to the PCIe slot 840. For example, PCIe slot 840 may be detected as empty if, LTSSM 810 is in the Detect state, Polling state, or Configuration state, and a previous state was the Polling state.

MISCTRLSTS register 886 may mask the Polling indication and Configuration indication by providing two control bits to AND gate 850 and/or AND gate 855. NOR gate 860 may provide “1” only if LTSSM 810 is in one of its states and not bouncing from state to state (e.g., Detect, Polling, Configuration).

According to some embodiments, MISCTRLSTS register 886 may provide a control bit 857 to MUX 870 in order to select between In-band hot-plug event detection, Out-of-band hot-plug event detection, or both, for example, to identify the presence of PCIe device in PCIe slot 840. The “Presence Detect” signal may be captured in SLOTSTS register 882 and any changes to the “Presence Detect” is also captured in SLOTSTS register 882. Changes in the “Presence Detect” status in SLOTSTS register 882 may trigger a PCI hot plug event to a Hot Plug driver.

According to some embodiments, the In-band hot-plug detection mechanism is configured to prevent spurious hot-plug events by masking the Detect indication bit, Polling indication bit or configuration indication bit, and allowing only one state of LTSSM 810 to be used.

Turning to FIG. 9, a demonstrative embodiment of a method 900 to detect a hot-plug event is shown. Method 900 may start with selection of a hot-plug detection method. In diamond 910 the method may include selecting an In-band hot-plug detection method/mechanism, an out-of-band hot-plug method/mechanism, or both.

According to the in-band mechanism, insertion and/or removal of a PCIe device from a PCIe slot (text box 920) may trigger a hot-plug event. A state machine, for example a PCIe LTSSM may detect the hot-plug event (text box 930).

According to one demonstrative embodiment, in order to generate a hot-plug detect message, the PCIe LTSSM may move between at least three states, e.g., Detect state, Polling state and Configuration state. In order to prevent generation of spurious messages and/or falls detection inductions of Polling state and/or Configuration state may be masked.

For example, when the LTSSM is in the Detect state, the Polling and Configuration indications may be masked (text box 940). When the LTSSM is in the Polling state, the Configuration indication may be masked (text box 950). When the LTSSM is in the Configuration state, the Polling indication may be masked (text box 960). When the hot-plug event detection is completed, a hot-plug event message may be generated to notify, for example, to computer system, of the occurrence of the hot-plug event (text box 970). Although it should be understood that embodiments are not limited to this example.

According to another demonstrative embodiment, in the out-of-band hot-plug detection mechanism, insertion or removal, for example, of a PCIe device from a PCIe slot (text box 980) may be detected, the VPP logic may generate a hot-plug event message to notify of the occurrence of the hot plug event to a computer system (text box 970). Although it should be understood that embodiments are not limited to this example.

Note that the apparatus′, methods′, and systems described above may be implemented in any electronic device or system as aforementioned. As specific illustrations, the figure below provides exemplary systems for utilizing some embodiments as described herein. As the systems below are described in more detail, a number of different interconnects are disclosed, described, and revisited from the discussion above. And as is readily apparent, the advances described above may be applied to any of those interconnects, fabrics, or architectures.

Referring now to FIG. 10, a block diagram of a system 1000 in accordance with an embodiment is shown. As shown in FIG. 10, multiprocessor system 1000 is a point-to-point interconnect system, and includes a first processor 1070 and a second processor 1080 coupled via a point-to-point interconnect 1050. Each of processors 1070 and 1080 may be some version of a processor. In one embodiment, the elements 1052 and 1054 are part of a serial, point-to-point coherent interconnect fabric, such as Intel's Quick Path Interconnect (QPI) architecture. As a result, some embodiments may be implemented within the QPI architecture.

While shown with only two processors 1070, 1080, it is to be understood that the scope of the present disclosure is not so limited. In other embodiments, one or more additional processors may be present in a given processor.

Processors 1070 and 1080 are shown including integrated memory controller units 1072 and 1082, respectively. Processor 1070 also includes as part of its bus controller units point-to-point (P-P) interfaces 1076 and 1078; similarly, second processor 1080 includes P-P interfaces 1086 and 1088. Processors 1070, 1080 may exchange information via a point-to-point (P-P) interface 1050 using P-P interface circuits 1078, 1088. As shown in FIG. 10, IMCs 1072 and 1082 couple the processors to respective memories, namely a memory 1032 and a memory 1034, which may be portions of main memory locally attached to the respective processors.

Processors 1070, 1080 each exchange information with a chipset 1090 via individual P-P interfaces 1052, 1054 using point to point interface circuits 1076, 1094, 1086, and 1098. Chipset 1090 also exchanges information with a high-performance graphics circuit 1038 via an interface circuit 1092 along a high-performance graphics interconnect 1039.

A shared cache (not shown) may be included in either processor or outside of both processors; yet connected with the processors via P-P interconnect, such that either or both processors' local cache information may be stored in the shared cache if a processor is placed into a low power mode.

Chipset 1090 may be coupled to a first bus 1016 via an interface 1096. In one embodiment, first bus 1016 may be a Peripheral Component Interconnect (PCI) bus, or a bus such as a PCI Express bus or another third generation I/O interconnect bus, although the scope of the present disclosure is not so limited.

As shown in FIG. 10, various I/O devices 1014 are coupled to first bus 1016, along with a bus bridge 1018, which couples first bus 1016 to a second bus 1020. In one embodiment, second bus 1020 includes a low pin count (LPC) bus. Various devices are coupled to second bus 1020 including, for example, a keyboard and/or mouse 1022, communication devices 1027 and a storage unit 1028 such as a disk drive or other mass storage device, which often includes instructions/code and data 1030, in one embodiment. Further, an audio I/O 1024 is shown coupled to second bus 1020. Note that other architectures are possible, where the included components and interconnect architectures vary. For example, instead of the point-to-point architecture of FIG. 10, a system may implement a multi-drop bus or other such architecture.

Referring now to FIG. 11, a block diagram of components of a computer system 1100 in accordance with an embodiment of the present disclosure is illustrated. As shown in FIG. 11, system 1100 includes a combination of components. These components may be implemented as Integrated Circuits (ICs), portions thereof, discrete electronic devices, and/or other modules, logic, hardware, software, firmware, or a combination thereof adapted in a computer system, or as components otherwise incorporated within a chassis of the computer system. Note also that the block diagram of FIG. 11 is intended to show a high level view of many components of the computer system. However, it is to be understood that some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations. As a result, the disclosure described above may be implemented in any portion of one or more of the interconnects illustrated or described below.

As shown in FIG. 11, a processor 1110, in one embodiment, includes a microprocessor, multi-core processor, multithreaded processor, an ultra low voltage processor, an embedded processor, and/or other known processing element. In the illustrated implementation, processor 1110 acts as a main processing unit and central hub for communication with many of the various components of the system 1100. As one example, processor 1110 is implemented as a system on a chip (SoC). As a specific illustrative example, processor 1110 includes an Intel® Architecture Core™-based processor such as an i3, i5, i7 or another such processor available from Intel Corporation, Santa Clara, Calif. However, understand that other low power processors such as available from Advanced Micro Devices, Inc. (AMD) of Sunnyvale, Calif., a MIPS-based design from MIPS Technologies, Inc. of Sunnyvale, Calif., an ARM-based design licensed from ARM Holdings, Ltd. or customer thereof, or their licensees or adopters may instead be present in other embodiments such as an Apple A5/A6 processor, a Qualcomm Snapdragon processor, or TI OMAP processor. Note that many of the customer versions of such processors are modified and varied; however, they may support or recognize a specific instructions set that performs defined algorithms as set forth by the processor licensor. Here, the microarchitectural implementation may vary, but the architectural function of the processor is usually consistent. Certain details regarding the architecture and operation of processor 1110 in one implementation will be discussed further below to provide an illustrative example.

Processor 1110, in one embodiment, communicates with a system memory 1115. As an illustrative example, which in an embodiment can be implemented via multiple memory devices to provide for a given amount of system memory. As examples, the memory can be in accordance with a Joint Electron Devices Engineering Council (JEDEC) low power double data rate (LPDDR)-based design such as the current LPDDR2 standard according to JEDEC JESD 209-2E (published April 2009), or a next generation LPDDR standard to be referred to as LPDDR3 or LPDDR4 that will offer extensions to LPDDR2 to increase bandwidth. In various implementations the individual memory devices may be of different package types such as single die package (SDP), dual die package (DDP) or quad die package (Q17P). These devices, in some embodiments, are directly soldered onto a motherboard to provide a lower profile solution, while in other embodiments the devices are configured as one or more memory modules that in turn couple to the motherboard by a given connector. And of course, other memory implementations are possible such as other types of memory modules, e.g., dual inline memory modules (DIMMs) of different varieties including but not limited to microDlMMs, MiniDIMMs. In a particular illustrative embodiment, memory is sized between 2 GB and 16 GB, and may be configured as a DDR3LM package or an LPDDR2 or LPDDR3 memory that is soldered onto a motherboard via a ball grid array (BGA).

To provide for persistent storage of information such as data, applications, one or more operating systems and so forth, a mass storage 1120 may also couple to processor 1110. In various embodiments, to enable a thinner and lighter system design as well as to improve system responsiveness, this mass storage may be implemented via a SSD. However in other embodiments, the mass storage may primarily be implemented using a hard disk drive (HDD) with a smaller amount of SSD storage to act as a SSD cache to enable non-volatile storage of context state and other such information during power down events so that a fast power up can occur on re-initiation of system activities. Also shown in FIG. 11, a flash device 1122 may be coupled to processor 1110, e.g., via a serial peripheral interface (SPI). This flash device may provide for non-volatile storage of system software, including a basic input/output software (BIOS) as well as other firmware of the system.

In various embodiments, mass storage of the system is implemented by a SSD alone or as a disk, optical or other drive with an SSD cache. In some embodiments, the mass storage is implemented as a SSD or as a HDD along with a restore (RST) cache module. In various implementations, the HDD provides for storage of between 320 GB-4 terabytes (TB) and upward while the RST cache is implemented with a SSD having a capacity of 24 GB-256 GB. Note that such SSD cache may be configured as a single level cache (SLC) or multi-level cache (MLC) option to provide an appropriate level of responsiveness. In a SSD-only option, the module may be accommodated in various locations such as in a mSATA or NGFF slot. As an example, an SSD has a capacity ranging from 120 GB-1 TB.

Various input/output (IO) devices may be present within system 1100. Specifically shown in the embodiment of FIG. 11 is a display 1124, which may be a high definition LCD or LED panel configured within a lid portion of the chassis. This display panel may also provide for a touch screen 1125, e.g., adapted externally over the display panel such that via a user's interaction with this touch screen, user inputs can be provided to the system to enable desired operations, e.g., with regard to the display of information, accessing of information and so forth. In one embodiment, display 1124 may be coupled to processor 1110 via a display interconnect that can be implemented as a high performance graphics interconnect. Touch screen 1125 may be coupled to processor 1110 via another interconnect, which in an embodiment can be an I²C interconnect. As further shown in FIG. 11, in addition to touch screen 1125, user input by way of touch can also occur via a touch pad 1130 which may be configured within the chassis and may also be coupled to the same I²C interconnect as touch screen 1125.

The display panel may operate in multiple modes. In a first mode, the display panel can be arranged in a transparent state in which the display panel is transparent to visible light. In various embodiments, the majority of the display panel may be a display except for a bezel around the periphery. When the system is operated in a notebook mode and the display panel is operated in a transparent state, a user may view information that is presented on the display panel while also being able to view objects behind the display. In addition, information displayed on the display panel may be viewed by a user positioned behind the display. Or the operating state of the display panel can be an opaque state in which visible light does not transmit through the display panel.

In a tablet mode the system is folded shut such that the back display surface of the display panel comes to rest in a position such that it faces outwardly towards a user, when the bottom surface of the base panel is rested on a surface or held by the user. In the tablet mode of operation, the back display surface performs the role of a display and user interface, as this surface may have touch screen functionality and may perform other known functions of a conventional touch screen device, such as a tablet device. To this end, the display panel may include a transparency-adjusting layer that is disposed between a touch screen layer and a front display surface. In some embodiments the transparency-adjusting layer may be an electrochromic layer (EC), a LCD layer, or a combination of EC and LCD layers.

In various embodiments, the display can be of different sizes, e.g., an 11.6″ or a 13.3″ screen, and may have a 16:9 aspect ratio, and at least 300 nits brightness. Also the display may be of full high definition (HD) resolution (at least 1920×1080p), be compatible with an embedded display port (eDP), and be a low power panel with panel self refresh.

As to touch screen capabilities, the system may provide for a display multi-touch panel that is multi-touch capacitive and being at least 5 finger capable. And in some embodiments, the display may be 10 finger capable. In one embodiment, the touch screen is accommodated within a damage and scratch-resistant glass and coating (e.g., Gorilla Glass™ or Gorilla Glass 2™) for low friction to reduce “finger burn” and avoid “finger skipping”. To provide for an enhanced touch experience and responsiveness, the touch panel, in some implementations, has multi-touch functionality, such as less than 2 frames (30 Hz) per static view during pinch zoom, and single-touch functionality of less than 1 cm per frame (30 Hz) with 200 ms (lag on finger to pointer). The display, in some implementations, supports edge-to-edge glass with a minimal screen bezel that is also flush with the panel surface, and limited IO interference when using multi-touch.

For perceptual computing and other purposes, various sensors may be present within the system and may be coupled to processor 1110 in different manners. Certain inertial and environmental sensors may couple to processor 1110 through a sensor hub 1140, e.g., via an I²C interconnect. In the embodiment shown in FIG. 11, these sensors may include an accelerometer 1141, an ambient light sensor (ALS) 1142, a compass 1143 and a gyroscope 1144. Other environmental sensors may include one or more thermal sensors 1146, which in some embodiments couple to processor 1110 via a system management bus (SMBus) bus.

Using the various inertial and environmental sensors present in a platform, many different use cases may be realized. These use cases enable advanced computing operations including perceptual computing and also allow for enhancements with regard to power management/battery life, security, and system responsiveness.

For example with regard to power management/battery life issues, based at least on part on information from an ambient light sensor, the ambient light conditions in a location of the platform are determined and intensity of the display controlled accordingly. Thus, power consumed in operating the display is reduced in certain light conditions.

As to security operations, based on context information obtained from the sensors such as location information, it may be determined whether a user is allowed to access certain secure documents. For example, a user may be permitted to access such documents at a work place or a home location. However, the user is prevented from accessing such documents when the platform is present at a public location. This determination, in one embodiment, is based on location information, e.g., determined via a GPS sensor or camera recognition of landmarks. Other security operations may include providing for pairing of devices within a close range of each other, e.g., a portable platform as described herein and a user's desktop computer, mobile telephone or so forth. Certain sharing, in some implementations, are realized via near field communication when these devices are so paired. However, when the devices exceed a certain range, such sharing may be disabled. Furthermore, when pairing a platform as described herein and a smartphone, an alarm may be configured to be triggered when the devices move more than a predetermined distance from each other, when in a public location. In contrast, when these paired devices are in a safe location, e.g., a work place or home location, the devices may exceed this predetermined limit without triggering such alarm.

Responsiveness may also be enhanced using the sensor information. For example, even when a platform is in a low power state, the sensors may still be enabled to run at a relatively low frequency. Accordingly, any changes in a location of the platform, e.g., as determined by inertial sensors, GPS sensor, or so forth is determined. If no such changes have been registered, a faster connection to a previous wireless hub such as a Wi-Fi™ access point or similar wireless enabler occurs, as there is no need to scan for available wireless network resources in this case. Thus, a greater level of responsiveness when waking from a low power state is achieved.

It is to be understood that many other use cases may be enabled using sensor information obtained via the integrated sensors within a platform as described herein, and the above examples are only for purposes of illustration. Using a system as described herein, a perceptual computing system may allow for the addition of alternative input modalities, including gesture recognition, and enable the system to sense user operations and intent.

In some embodiments one or more infrared or other heat sensing elements, or any other element for sensing the presence or movement of a user may be present. Such sensing elements may include multiple different elements working together, working in sequence, or both. For example, sensing elements include elements that provide initial sensing, such as light or sound projection, followed by sensing for gesture detection by, for example, an ultrasonic time of flight camera or a patterned light camera.

Also in some embodiments, the system includes a light generator to produce an illuminated line. In some embodiments, this line provides a visual cue regarding a virtual boundary, namely an imaginary or virtual location in space, where action of the user to pass or break through the virtual boundary or plane is interpreted as an intent to engage with the computing system. In some embodiments, the illuminated line may change colors as the computing system transitions into different states with regard to the user. The illuminated line may be used to provide a visual cue for the user of a virtual boundary in space, and may be used by the system to determine transitions in state of the computer with regard to the user, including determining when the user wishes to engage with the computer.

In some embodiments, the computer senses user position and operates to interpret the movement of a hand of the user through the virtual boundary as a gesture indicating an intention of the user to engage with the computer. In some embodiments, upon the user passing through the virtual line or plane the light generated by the light generator may change, thereby providing visual feedback to the user that the user has entered an area for providing gestures to provide input to the computer.

Display screens may provide visual indications of transitions of state of the computing system with regard to a user. In some embodiments, a first screen is provided in a first state in which the presence of a user is sensed by the system, such as through use of one or more of the sensing elements.

In some implementations, the system acts to sense user identity, such as by facial recognition. Here, transition to a second screen may be provided in a second state, in which the computing system has recognized the user identity, where this second the screen provides visual feedback to the user that the user has transitioned into a new state. Transition to a third screen may occur in a third state in which the user has confirmed recognition of the user.

In some embodiments, the computing system may use a transition mechanism to determine a location of a virtual boundary for a user, where the location of the virtual boundary may vary with user and context. The computing system may generate a light, such as an illuminated line, to indicate the virtual boundary for engaging with the system. In some embodiments, the computing system may be in a waiting state, and the light may be produced in a first color. The computing system may detect whether the user has reached past the virtual boundary, such as by sensing the presence and movement of the user using sensing elements.

In some embodiments, if the user has been detected as having crossed the virtual boundary (such as the hands of the user being closer to the computing system than the virtual boundary line), the computing system may transition to a state for receiving gesture inputs from the user, where a mechanism to indicate the transition may include the light indicating the virtual boundary changing to a second color.

In some embodiments, the computing system may then determine whether gesture movement is detected. If gesture movement is detected, the computing system may proceed with a gesture recognition process, which may include the use of data from a gesture data library, which may reside in memory in the computing device or may be otherwise accessed by the computing device.

If a gesture of the user is recognized, the computing system may perform a function in response to the input, and return to receive additional gestures if the user is within the virtual boundary. In some embodiments, if the gesture is not recognized, the computing system may transition into an error state, where a mechanism to indicate the error state may include the light indicating the virtual boundary changing to a third color, with the system returning to receive additional gestures if the user is within the virtual boundary for engaging with the computing system.

As mentioned above, in other embodiments the system can be configured as a convertible tablet system that can be used in at least two different modes, a tablet mode and a notebook mode. The convertible system may have two panels, namely a display panel and a base panel such that in the tablet mode the two panels are disposed in a stack on top of one another. In the tablet mode, the display panel faces outwardly and may provide touch screen functionality as found in conventional tablets. In the notebook mode, the two panels may be arranged in an open clamshell configuration.

In various embodiments, the accelerometer may be a 3-axis accelerometer having data rates of at least 50 Hz. A gyroscope may also be included, which can be a 3-axis gyroscope. In addition, an e-compass/magnetometer may be present. Also, one or more proximity sensors may be provided (e.g., for lid open to sense when a person is in proximity (or not) to the system and adjust power/performance to extend battery life). For some OS's Sensor Fusion capability including the accelerometer, gyroscope, and compass may provide enhanced features. In addition, via a sensor hub having a real-time clock (RTC), a wake from sensors mechanism may be realized to receive sensor input when a remainder of the system is in a low power state.

In some embodiments, an internal lid/display open switch or sensor to indicate when the lid is closed/open, and can be used to place the system into Connected Standby or automatically wake from Connected Standby state. Other system sensors can include ACPI sensors for internal processor, memory, and skin temperature monitoring to enable changes to processor and system operating states based on sensed parameters.

In an embodiment, the OS may be a Microsoft® Windows® 8 OS that implements Connected Standby (also referred to herein as Win8 CS). Windows 8 Connected Standby or another OS having a similar state can provide, via a platform as described herein, very low ultra idle power to enable applications to remain connected, e.g., to a cloud-based location, at very low power consumption. The platform can supports 3 power states, namely screen on (normal); Connected Standby (as a default “off” state); and shutdown (zero watts of power consumption). Thus in the Connected Standby state, the platform is logically on (at minimal power levels) even though the screen is off. In such a platform, power management can be made to be transparent to applications and maintain constant connectivity, in part due to offload technology to enable the lowest powered component to perform an operation.

Also seen in FIG. 11, various peripheral devices may couple to processor 1110 via a low pin count (LPC) interconnect. In the embodiment shown, various components can be coupled through an embedded controller 1135. Such components can include a keyboard 1136 (e.g., coupled via a PS2 interface), a fan 1137, and a thermal sensor 1139. In some embodiments, touch pad 1130 may also couple to EC 1135 via a PS2 interface. In addition, a security processor such as a trusted platform module (TPM) 1138 in accordance with the Trusted Computing Group (TCG) TPM Specification Version 1.2, dated Oct. 2, 2003, may also couple to processor 1110 via this LPC interconnect. However, understand the scope of the present disclosure is not limited in this regard and secure processing and storage of secure information may be in another protected location such as a static random access memory (SRAM) in a security coprocessor, or as encrypted data blobs that are only decrypted when protected by a secure enclave (SE) processor mode.

In a particular implementation, peripheral ports may include a high definition media interface (HDMI) connector (which can be of different form factors such as full size, mini or micro); one or more USB ports, such as full-size external ports in accordance with the Universal Serial Bus Revision 3.0 Specification (November 2008), with at least one powered for charging of USB devices (such as smartphones) when the system is in Connected Standby state and is plugged into AC wall power. In addition, one or more Thunderbolt™ ports can be provided. Other ports may include an externally accessible card reader such as a full size SD-XC card reader and/or a SIM card reader for WWAN (e.g., an 8 pin card reader). For audio, a 3.5 mm jack with stereo sound and microphone capability (e.g., combination functionality) can be present, with support for jack detection (e.g., headphone only support using microphone in the lid or headphone with microphone in cable). In some embodiments, this jack can be re-taskable between stereo headphone and stereo microphone input. Also, a power jack can be provided for coupling to an AC brick.

System 1100 can communicate with external devices in a variety of manners, including wirelessly. In the embodiment shown in FIG. 11, various wireless modules, each of which can correspond to a radio configured for a particular wireless communication protocol, are present. One manner for wireless communication in a short range such as a near field may be via a near field communication (NFC) unit 1145 which may communicate, in one embodiment with processor 1110 via an SMBus. Note that via this NFC unit 1145, devices in close proximity to each other can communicate. For example, a user can enable system 1100 to communicate with another (e.g.,) portable device such as a smartphone of the user via adapting the two devices together in close relation and enabling transfer of information such as identification information payment information, data such as image data or so forth. Wireless power transfer may also be performed using a NFC system.

Using the NFC unit described herein, users can bump devices side-to-side and place devices side-by-side for near field coupling functions (such as near field communication and wireless power transfer (WPT)) by leveraging the coupling between coils of one or more of such devices. More specifically, embodiments provide devices with strategically shaped, and placed, ferrite materials, to provide for better coupling of the coils. Each coil has an inductance associated with it, which can be chosen in conjunction with the resistive, capacitive, and other features of the system to enable a common resonant frequency for the system.

As further seen in FIG. 11, additional wireless units can include other short range wireless engines including a WLAN unit 1150 and a Bluetooth unit 1152. Using WLAN unit 1150, Wi-Fi™ communications in accordance with a given Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard can be realized, while via Bluetooth unit 1152, short range communications via a Bluetooth protocol can occur. These units may communicate with processor 1110 via, e.g., a USB link or a universal asynchronous receiver transmitter (UART) link. Or these units may couple to processor 1110 via an interconnect according to a Peripheral Component Interconnect Express™ (PCIe™) protocol, e.g., in accordance with the PCI Express™ Specification Base Specification version 3.0 (published Jan. 17, 2007), or another such protocol such as a serial data input/output (SDIO) standard. Of course, the actual physical connection between these peripheral devices, which may be configured on one or more add-in cards, can be by way of the NGFF connectors adapted to a motherboard.

In addition, wireless wide area communications, e.g., according to a cellular or other wireless wide area protocol, can occur via a WWAN unit 1156 which in turn may couple to a subscriber identity module (SIM) 1157. In addition, to enable receipt and use of location information, a GPS module 1155 may also be present. Note that in the embodiment shown in FIG. 11, WWAN unit 1156 and an integrated capture device such as a camera module 1154 may communicate via a given USB protocol such as a USB 2.0 or 3.0 link, or a UART or I²C protocol. Again the actual physical connection of these units can be via adaptation of a Next Generation Form Factor (NGFF) add-in card to an NGFF connector configured on the motherboard.

In a particular embodiment, wireless functionality can be provided modularly, e.g., with a WiFi™ 802.11ac solution (e.g., add-in card that is backward compatible with IEEE 802.11abgn) with support for Windows 8 CS. This card can be configured in an internal slot (e.g., via an NGFF adapter). An additional module may provide for Bluetooth capability (e.g., Bluetooth 4.0 with backwards compatibility) as well as Intel® Wireless Display functionality. In addition NFC support may be provided via a separate device or multi-function device, and can be positioned as an example, in a front right portion of the chassis for easy access. A still additional module may be a WWAN device that can provide support for 3G/4G/LTE and GPS. This module can be implemented in an internal (e.g., NGFF) slot. Integrated antenna support can be provided for WiFi™, Bluetooth, WWAN, NFC and GPS, enabling seamless transition from WiFi™ to WWAN radios, wireless gigabit (WiGig) in accordance with the Wireless Gigabit Specification (July 2010), and vice versa.

As described above, an integrated camera can be incorporated in the lid. As one example, this camera can be a high resolution camera, e.g., having a resolution of at least 2.0 megapixels (MP) and extending to 6.0 MP and beyond.

To provide for audio inputs and outputs, an audio processor can be implemented via a digital signal processor (DSP) 1160, which may couple to processor 1110 via a high definition audio (HDA) link. Similarly, DSP 1160 may communicate with an integrated coder/decoder (CODEC) and amplifier 1162 that in turn may couple to output speakers 1163 which may be implemented within the chassis. Similarly, amplifier and CODEC 1162 can be coupled to receive audio inputs from a microphone 1165 which in an embodiment can be implemented via dual array microphones (such as a digital microphone array) to provide for high quality audio inputs to enable voice-activated control of various operations within the system. Note also that audio outputs can be provided from amplifier/CODEC 1162 to a headphone jack 1164. Although shown with these particular components in the embodiment of FIG. 11, understand the scope of the present disclosure is not limited in this regard.

In a particular embodiment, the digital audio codec and amplifier are capable of driving the stereo headphone jack, stereo microphone jack, an internal microphone array and stereo speakers. In different implementations, the codec can be integrated into an audio DSP or coupled via an HD audio path to a peripheral controller hub (PCH). In some implementations, in addition to integrated stereo speakers, one or more bass speakers can be provided, and the speaker solution can support DTS audio.

In some embodiments, processor 1110 may be powered by an external voltage regulator (VR) and multiple internal voltage regulators that are integrated inside the processor die, referred to as fully integrated voltage regulators (FIVRs). The use of multiple FIVRs in the processor enables the grouping of components into separate power planes, such that power is regulated and supplied by the FIVR to only those components in the group. During power management, a given power plane of one FIVR may be powered down or off when the processor is placed into a certain low power state, while another power plane of another FIVR remains active, or fully powered.

In one embodiment, a sustain power plane can be used during some deep sleep states to power on the I/O pins for several I/O signals, such as the interface between the processor and a PCH, the interface with the external VR and the interface with EC 1135. This sustain power plane also powers an on-die voltage regulator that supports the on-board SRAM or other cache memory in which the processor context is stored during the sleep state. The sustain power plane is also used to power on the processor's wakeup logic that monitors and processes the various wakeup source signals.

During power management, while other power planes are powered down or off when the processor enters certain deep sleep states, the sustain power plane remains powered on to support the above-referenced components. However, this can lead to unnecessary power consumption or dissipation when those components are not needed. To this end, embodiments may provide a connected standby sleep state to maintain processor context using a dedicated power plane. In one embodiment, the connected standby sleep state facilitates processor wakeup using resources of a PCH which itself may be present in a package with the processor. In one embodiment, the connected standby sleep state facilitates sustaining processor architectural functions in the PCH until processor wakeup, this enabling turning off all of the unnecessary processor components that were previously left powered on during deep sleep states, including turning off all of the clocks. In one embodiment, the PCH contains a time stamp counter (TSC) and connected standby logic for controlling the system during the connected standby state. The integrated voltage regulator for the sustain power plane may reside on the PCH as well.

In an embodiment, during the connected standby state, an integrated voltage regulator may function as a dedicated power plane that remains powered on to support the dedicated cache memory in which the processor context is stored such as critical state variables when the processor enters the deep sleep states and connected standby state. This critical state may include state variables associated with the architectural, micro-architectural, debug state, and/or similar state variables associated with the processor.

The wakeup source signals from EC 1135 may be sent to the PCH instead of the processor during the connected standby state so that the PCH can manage the wakeup processing instead of the processor. In addition, the TSC is maintained in the PCH to facilitate sustaining processor architectural functions. Although shown with these particular components in the embodiment of FIG. 11, understand the scope of the present disclosure is not limited in this regard.

Power control in the processor can lead to enhanced power savings. For example, power can be dynamically allocate between cores, individual cores can change frequency/voltage, and multiple deep low power states can be provided to enable very low power consumption. In addition, dynamic control of the cores or independent core portions can provide for reduced power consumption by powering off components when they are not being used.

Some implementations may provide a specific power management IC (PMIC) to control platform power. Using this solution, a system may see very low (e.g., less than 5%) battery degradation over an extended duration (e.g., 16 hours) when in a given standby state, such as when in a Win8 Connected Standby state. In a Win8 idle state a battery life exceeding, e.g., 9 hours may be realized (e.g., at 150 nits). As to video playback, a long battery life can be realized, e.g., full HD video playback can occur for a minimum of 6 hours. A platform in one implementation may have an energy capacity of, e.g., 35 watt hours (Whr) for a Win8 CS using an SSD and (e.g.,) 40-44Whr for Win8 CS using an HDD with a RST cache configuration.

A particular implementation may provide support for 15 W nominal CPU thermal design power (TDP), with a configurable CPU TDP of up to approximately 25 W TDP design point. The platform may include minimal vents owing to the thermal features described above. In addition, the platform is pillow-friendly (in that no hot air is blowing at the user). Different maximum temperature points can be realized depending on the chassis material. In one implementation of a plastic chassis (at least having to lid or base portion of plastic), the maximum operating temperature can be 52 degrees Celsius (C). And for an implementation of a metal chassis, the maximum operating temperature can be 46° C.

In different implementations, a security module such as a TPM can be integrated into a processor or can be a discrete device such as a TPM 2.0 device. With an integrated security module, also referred to as Platform Trust Technology (PTT), BIOS/firmware can be enabled to expose certain hardware features for certain security features, including secure instructions, secure boot, Intel® Anti-Theft Technology, Intel® Identity Protection Technology, Intel® Trusted Execution Technology (TXT), and Intel® Manageability Engine Technology along with secure user interfaces such as a secure keyboard and display.

Examples

The following examples pertain to further embodiments.

Example 1 includes an apparatus comprising a processor; a bus operably coupled to the processor; an extension bus slot operably coupled to the bus; and a circuitry to detect a hot-plug event when inserting or removing a device from the extension bus slot, and to generate a hot-plug message to notify of an occurrence of the hot-plug event, the circuitry comprising a state machine to detect the hot-plug event; and a register to provide at least two bits to mask at least two states of the state machine.

Example 2 includes the subject matter of Example 1, and optionally, wherein the register is to select between an in-band hot-plug detection and an out-of-band hot-plug detection.

Example 3 includes the subject matter of Example 1, and optionally, wherein the register is to select both an in-band hot-plug detection and an out-of-band hot-plug detection.

Example 4 includes the subject matter of any one of Examples 1-3, and optionally, wherein the extension bus slot comprises a Peripheral Component Interconnect express (PCIe) slot.

Example 5 includes the subject matter of any one of Examples 1-4, and optionally, wherein the device comprises a Peripheral Component Interconnect express (PCIe) device.

Example 6 includes the subject matter of any one of Examples 1-5, and optionally, wherein the state machine comprises a Peripheral Component Interconnect express (PCIe) link training and status state machine (LTSSM), the PCIe LTSSM is to be in at least one of a Detect state, a Polling state or a Configuration state.

Example 7 includes the subject matter of Example 6, and optionally, wherein the register is to mask a Polling state indication and a Configuration state indication of the PCIe LTSSM.

Example 8 includes the subject matter of any one of Examples 1-7, and optionally, comprising a virtual port pin (VPP) logic to provide an out of band hot-plug event detection indication.

Example 9 includes a method comprising selecting between an in-band hot-plug detection mechanism, an out-of-band hot-plug detection mechanism, or both the in-band hot-plug detection and the out-of-band hot-plug detection; detecting a hot-plug event when inserting or removing a device from an extension bus slot, wherein according to the in-band hot-plug detection mechanism, detecting the hot-plug event is by a state machine having at least three states and by masking at least two states of the state machine; and generating a hot-plug event message to notify of an occurrence of the hot-plug event.

Example 10 includes the subject matter of Example 9, and optionally, wherein the extension bus slot comprises a Peripheral Component Interconnect express (PCIe) slot.

Example 11 includes the subject matter of Example 9 or 10, and optionally, wherein the device comprises a Peripheral Component Interconnect express (PCIe) device.

Example 12 includes the subject matter of any one of Examples 9-11, and optionally, wherein the state machine comprises a Peripheral Component Interconnect express (PCIe) link training and status state machine (LTSSM), the PCIe LTSSM is to be in at least one of a Detect state, a Polling state or a Configuration state.

Example 13 includes the subject matter of Example 12, and optionally, wherein masking comprises masking a Polling state indication or a Configuration state indication of the PCIe LTSSM.

Example 14 includes the subject matter of any one of Examples 9-13, and optionally, wherein according to the out-of-band detection mechanism, detecting the hot-plug event is by a virtual port pin (VPP) logic and by writing a detection of a hot-plug event status into a register.

Example 15 includes a system comprising an apparatus comprising a processor; a plurality of buses operably coupled to the processor; a plurality of extension bus slots operably coupled to the plurality of buses; and a circuitry to detect a hot-plug event when inserting or removing a device from an extension bus slot of the plurality of extension bus slots, and to generate a hot-plug message to notify of an occurrence of the hot-plug event, the circuitry comprising a state machine to detect the hot-plug event; and a register to provide at least two bits to mask at least two states of the state machine.

Example 16 includes the subject matter of Example 15, and optionally, wherein the register is to select between an in-band hot-plug detection and an out-of-band hot-plug detection.

Example 17 includes the subject matter of Example 15, and optionally, wherein the register is to select both an in-band hot-plug detection and an out-of-band hot-plug detection.

Example 18 includes the subject matter of any one of Examples 15-17, and optionally, wherein the extension bus slot comprises a Peripheral Component Interconnect express (PCIe) slot.

Example 19 includes the subject matter of any one of Examples 15-18, and optionally, wherein the device comprises a Peripheral Component Interconnect express (PCIe) device.

Example 20 includes the subject matter of any one of Examples 15-19, and optionally, wherein the state machine comprises a Peripheral Component Interconnect express (PCIe) link training and status state machine (LTSSM), the PCIe LTSSM is to be in at least one of a Detect state, a Polling state or a Configuration state.

Example 21 includes the subject matter of Example 20, and optionally, wherein the register is to mask a Polling state indication and a Configuration state indication of the PCIe LTSSM.

Example 22 includes the subject matter of any one of Examples 15-21, and optionally, comprising a virtual port pin (VPP) logic to provide an out of band hot-plug event.

Example 23 includes a non-transitory storage medium having stored thereon instructions that, when executed by a machine, result in selecting between an in-band hot-plug detection mechanism, an out-of-band hot-plug detection mechanism, or both the in-band hot-plug detection and the out-of-band hot-plug detection; detecting a hot-plug event when inserting or removing a device from an extension bus slot, wherein according to the in-band hot-plug detection mechanism, detecting the hot-plug event is by a state machine having at least three states and by masking at least two states of the state machine; and generating a hot-plug event message to notify of an occurrence of the hot-plug event.

Example 24 includes the subject matter of Example 23, and optionally, wherein the extension bus slot comprises a Peripheral Component Interconnect express (PCIe) slot.

Example 25 includes the subject matter of Example 23 or 24, and optionally, wherein the device comprises a Peripheral Component Interconnect express (PCIe) device.

Example 26 includes the subject matter of any one of Examples 23-25, and optionally, wherein the state machine comprises a Peripheral Component Interconnect express (PCIe) link training and status state machine (LTSSM), the PCIe LTSSM is to be in at least one of a Detect state, a Polling state or a Configuration state.

Example 27 includes the subject matter of Example 26, and optionally, wherein masking comprises masking a Polling state indication or a Configuration state indication of the PCIe LTSSM.

Example 28 includes the subject matter of any one of Examples 23-27, and optionally, wherein according to the out-of-band detection mechanism, detecting the hot-plug event is by a virtual port pin (VPP) logic and by writing a detection of a hot-plug event status into a register.

Example 29 includes an apparatus of detecting an event at a computer bus, the apparatus comprising means for selecting between an in-band hot-plug detection mechanism, an out-of-band hot-plug detection mechanism, or both the in-band hot-plug detection and the out-of-band hot-plug detection; means for detecting a hot-plug event when inserting or removing a device from an extension bus slot, wherein according to the in-band hot-plug detection mechanism, detecting the hot-plug event is by a state machine having at least three states and by masking at least two states of the state machine; and means for generating a hot-plug event message to notify of an occurrence of the hot-plug event.

Example 30 includes the subject matter of Example 29, and optionally, wherein the extension bus slot comprises a Peripheral Component Interconnect express (PCIe) slot.

Example 31 includes the subject matter of Example 29 or 30, and optionally, wherein the device comprises a Peripheral Component Interconnect express (PCIe) device.

Example 32 includes the subject matter of any one of Examples 29-31, and optionally, wherein the state machine comprises a Peripheral Component Interconnect express (PCIe) link training and status state machine (LTSSM), the PCIe LTSSM is to be in at least one of a Detect state, a Polling state or a Configuration state.

Example 33 includes the subject matter of Example 32, and optionally, comprising means for masking a Polling state indication or a Configuration state indication of the PCIe LTSSM.

Example 34 includes the subject matter of any one of Examples 29-33, and optionally, wherein according to the out-of-band detection mechanism, detecting the hot-plug event is by a virtual port pin (VPP) logic and by writing a detection of a hot-plug event status into a register.

Example 35 includes the subject matter of any one of Examples 29-34, and optionally, comprising a motherboard.

Example 36 includes a motherboard comprising a processor; a plurality of buses operably coupled to the processor; a plurality of extension bus slots operably coupled to the plurality of buses; and a circuitry to detect a hot-plug event when inserting or removing a device from an extension bus slot of the plurality of extension bus slots, and to generate a hot-plug message to notify of an occurrence of the hot-plug event, the circuitry comprising a state machine to detect the hot-plug event; and a register to provide at least two bits to mask at least two states of the state machine.

Example 37 includes the subject matter of Example 36, and optionally, wherein the register is to select between an in-band hot-plug detection and an out-of-band hot-plug detection.

Example 38 includes the subject matter of Example 36, and optionally, wherein the register is to select both an in-band hot-plug detection and an out-of-band hot-plug detection.

Example 39 includes the subject matter of any one of Examples 36-38, and optionally, wherein the extension bus slot comprises a Peripheral Component Interconnect express (PCIe) slot.

Example 40 includes the subject matter of any one of Examples 36-39, and optionally, wherein the device comprises a Peripheral Component Interconnect express (PCIe) device.

Example 41 includes the subject matter of any one of Examples 36-40, and optionally, wherein the state machine comprises a Peripheral Component Interconnect express (PCIe) link training and status state machine (LTSSM), the PCIe LTSSM is to be in at least one of a Detect state, a Polling state or a Configuration state.

Example 42 includes the subject matter of Example 41, and optionally, wherein the register is to mask a Polling state indication and a Configuration state indication of the PCIe LTSSM.

Example 43 includes the subject matter of any one of Examples 36-42, and optionally, comprising a virtual port pin (VPP) logic to provide an out of band hot-plug event.

While the present disclosure has been described with respect to a limited number of embodiments, those skilled in the art will appreciate numerous modifications and variations therefrom. It is intended that the appended claims cover all such modifications and variations as fall within the true spirit and scope of this present disclosure.

A design may go through various stages, from creation to simulation to fabrication. Data representing a design may represent the design in a number of manners. First, as is useful in simulations, the hardware may be represented using a hardware description language or another functional description language. Additionally, a circuit level model with logic and/or transistor gates may be produced at some stages of the design process. Furthermore, most designs, at some stage, reach a level of data representing the physical placement of various devices in the hardware model. In the case where conventional semiconductor fabrication techniques are used, the data representing the hardware model may be the data specifying the presence or absence of various features on different mask layers for masks used to produce the integrated circuit. In any representation of the design, the data may be stored in any form of a machine readable medium. A memory or a magnetic or optical storage such as a disc may be the machine readable medium to store information transmitted via optical or electrical wave modulated or otherwise generated to transmit such information. When an electrical carrier wave indicating or carrying the code or design is transmitted, to the extent that copying, buffering, or re-transmission of the electrical signal is performed, a new copy is made. Thus, a communication provider or a network provider may store on a tangible, machine-readable medium, at least temporarily, an article, such as information encoded into a carrier wave, embodying techniques of embodiments of the present disclosure.

A module as used herein refers to any combination of hardware, software, and/or firmware. As an example, a module includes hardware, such as a micro-controller, associated with a non-transitory medium to store code adapted to be executed by the micro-controller. Therefore, reference to a module, in one embodiment, refers to the hardware, which is specifically configured to recognize and/or execute the code to be held on a non-transitory medium. Furthermore, in another embodiment, use of a module refers to the non-transitory medium including the code, which is specifically adapted to be executed by the microcontroller to perform predetermined operations. And as can be inferred, in yet another embodiment, the term module (in this example) may refer to the combination of the microcontroller and the non-transitory medium. Often module boundaries that are illustrated as separate commonly vary and potentially overlap. For example, a first and a second module may share hardware, software, firmware, or a combination thereof, while potentially retaining some independent hardware, software, or firmware. In one embodiment, use of the term logic includes hardware, such as transistors, registers, or other hardware, such as programmable logic devices.

Use of the phrase ‘to’ or ‘configured to,’ in one embodiment, refers to arranging, putting together, manufacturing, offering to sell, importing and/or designing an apparatus, hardware, logic, or element to perform a designated or determined task. In this example, an apparatus or element thereof that is not operating is still ‘configured to’ perform a designated task if it is designed, coupled, and/or interconnected to perform said designated task. As a purely illustrative example, a logic gate may provide a 0 or a 1 during operation. But a logic gate ‘configured to’ provide an enable signal to a clock does not include every potential logic gate that may provide a 1 or 0. Instead, the logic gate is one coupled in some manner that during operation the 1 or 0 output is to enable the clock. Note once again that use of the term ‘configured to’ does not require operation, but instead focus on the latent state of an apparatus, hardware, and/or element, where in the latent state the apparatus, hardware, and/or element is designed to perform a particular task when the apparatus, hardware, and/or element is operating.

Furthermore, use of the phrases ‘capable of/to,’ and or ‘operable to,’ in one embodiment, refers to some apparatus, logic, hardware, and/or element designed in such a way to enable use of the apparatus, logic, hardware, and/or element in a specified manner. Note as above that use of to, capable to, or operable to, in one embodiment, refers to the latent state of an apparatus, logic, hardware, and/or element, where the apparatus, logic, hardware, and/or element is not operating but is designed in such a manner to enable use of an apparatus in a specified manner.

A value, as used herein, includes any known representation of a number, a state, a logical state, or a binary logical state. Often, the use of logic levels, logic values, or logical values is also referred to as 1's and 0's, which simply represents binary logic states. For example, a 1 refers to a high logic level and 0 refers to a low logic level. In one embodiment, a storage cell, such as a transistor or flash cell, may be capable of holding a single logical value or multiple logical values. However, other representations of values in computer systems have been used. For example the decimal number ten may also be represented as a binary value of 1010 and a hexadecimal letter A. Therefore, a value includes any representation of information capable of being held in a computer system.

Moreover, states may be represented by values or portions of values. As an example, a first value, such as a logical one, may represent a default or initial state, while a second value, such as a logical zero, may represent a non-default state. In addition, the terms reset and set, in one embodiment, refer to a default and an updated value or state, respectively. For example, a default value potentially includes a high logical value, i.e. reset, while an updated value potentially includes a low logical value, i.e. set. Note that any combination of values may be utilized to represent any number of states.

The embodiments of methods, hardware, software, firmware or code set forth above may be implemented via instructions or code stored on a machine-accessible, machine readable, computer accessible, or computer readable medium which are executable by a processing element. A non-transitory machine-accessible/readable medium includes any mechanism that provides (i.e., stores and/or transmits) information in a form readable by a machine, such as a computer or electronic system. For example, a non-transitory machine-accessible medium includes random-access memory (RAM), such as static RAM (SRAM) or dynamic RAM (DRAM); ROM; magnetic or optical storage medium; flash memory devices; electrical storage devices; optical storage devices; acoustical storage devices; other form of storage devices for holding information received from transitory (propagated) signals (e.g., carrier waves, infrared signals, digital signals); etc, which are to be distinguished from the non-transitory mediums that may receive information there from.

Instructions used to program logic to perform some embodiments may be stored within a memory in the system, such as DRAM, cache, flash memory, or other storage. Furthermore, the instructions can be distributed via a network or by way of other computer readable media. Thus a machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), but is not limited to, floppy diskettes, optical disks, Compact Disc, Read-Only Memory (CD-ROMs), and magneto-optical disks, Read-Only Memory (ROMs), Random Access Memory (RAM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), magnetic or optical cards, flash memory, or a tangible, machine-readable storage used in the transmission of information over the Internet via electrical, optical, acoustical or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.). Accordingly, the computer-readable medium includes any type of tangible machine-readable medium suitable for storing or transmitting electronic instructions or information in a form readable by a machine (e.g., a computer)

Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

In the foregoing specification, a detailed description has been given with reference to specific exemplary embodiments. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the disclosure as set forth in the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense. Furthermore, the foregoing use of embodiment and other exemplarily language does not necessarily refer to the same embodiment or the same example, but may refer to different and distinct embodiments, as well as potentially the same embodiment. 

What is claimed is:
 1. An apparatus comprising: a processor; a bus operably coupled to the processor; an extension bus slot operably coupled to the bus; and a circuitry to detect a hot-plug event when inserting or removing a device from the extension bus slot, and to generate a hot-plug message to notify of an occurrence of the hot-plug event, the circuitry comprising: a state machine to detect the hot-plug event; and a register to provide at least two bits to mask at least two states of the state machine.
 2. The apparatus of claim 1, wherein the register is to select between an in-band hot-plug detection and an out-of-band hot-plug detection.
 3. The apparatus of claim 1, wherein the register is to select both an in-band hot-plug detection and an out-of-band hot-plug detection
 4. The apparatus of claim 1, wherein the extension bus slot comprises a Peripheral Component Interconnect express (PCIe) slot.
 5. The apparatus of claim 1, wherein the device comprises a Peripheral Component Interconnect express (PCIe) device.
 6. The apparatus of claim 1, wherein the state machine comprises a Peripheral Component Interconnect express (PCIe) link training and status state machine (LTSSM), the PCIe LTSSM is to be in at least one of a Detect state, a Polling state or a Configuration state.
 7. The apparatus of claim 6, wherein the register is to mask a Polling state indication and a Configuration state indication of the PCIe LTSSM.
 8. The apparatus of claim 1 comprising: a virtual port pin (VPP) logic to provide an out of band hot-plug event detection indication.
 9. A method comprising: selecting between an in-band hot-plug detection mechanism, an out-of-band hot-plug detection mechanism, or both the in-band hot-plug detection and the out-of-band hot-plug detection; detecting a hot-plug event when inserting or removing a device from an extension bus slot, wherein according to the in-band hot-plug detection mechanism, detecting the hot-plug event is by a state machine having at least three states and by masking at least two states of the state machine; and generating a hot-plug event message to notify of an occurrence of the hot-plug event.
 10. The method of claim 9, wherein the extension bus slot comprises a Peripheral Component Interconnect express (PCIe) slot.
 11. The method of claim 9, wherein the device comprises a Peripheral Component Interconnect express (PCIe) device.
 12. The method of claim 9, wherein the state machine comprises a Peripheral Component Interconnect express (PCIe) link training and status state machine (LTSSM), the PCIe LTSSM is to be in at least one of a Detect state, a Polling state or a Configuration state.
 13. The method of claim 12, wherein masking comprises: masking a Polling state indication or a Configuration state indication of the PCIe LTSSM.
 14. The method of claim 9, wherein according to the out-of-band detection mechanism, detecting the hot-plug event is by a virtual port pin (VPP) logic and by writing a detection of a hot-plug event status into a register.
 15. A system comprising: an apparatus comprising: a processor; a plurality of buses operably coupled to the processor; a plurality of extension bus slots operably coupled to the plurality of buses; and a circuitry to detect a hot-plug event when inserting or removing a device from an extension bus slot of the plurality of extension bus slots, and to generate a hot-plug message to notify of an occurrence of the hot-plug event, the circuitry comprising: a state machine to detect the hot-plug event; and a register to provide at least two bits to mask at least two states of the state machine.
 16. The system of claim 15, wherein the register is to select between an in-band hot-plug detection and an out-of-band hot-plug detection.
 17. The system of claim 15, wherein the register is to select both an in-band hot-plug detection and an out-of-band hot-plug detection
 18. The system of claim 15, wherein the extension bus slot comprises a Peripheral Component Interconnect express (PCIe) slot.
 19. The system of claim 15, wherein the device comprises a Peripheral Component Interconnect express (PCIe) device.
 20. The system of claim 15, wherein the state machine comprises a Peripheral Component Interconnect express (PCIe) link training and status state machine (LTSSM), the PCIe LTSSM is to be in at least one of a Detect state, a Polling state or a Configuration state.
 21. The system of claim 20, wherein the register is to mask a Polling state indication and a Configuration state indication of the PCIe LTSSM.
 22. The system of claim 15 comprising: a virtual port pin (VPP) logic to provide an out of band hot-plug event detection indication. 